Iguana – Technical requirements and advice
1 Server-side
1.1 Required servers
The following server platforms are supported:
· Operating System: Windows / Web server: Internet Information Services [IIS] (or possibly Apache)
· Operating System: Linux / Web server: Apache
· Operating System: Unix / Web server: Apache
Note: the operating systems and web servers must comply with the types / versions / editions of the operating system and web server which are supported by InterSystems Caché 2008.1.2 (for the database server) and Intersystems Caché 2010 (for the web server / Caché gateway). An overview of these requirements can be found at: http://www.intersystems.com/cache/technology/product-tables/current-prodlist.html.
1.2 Required disk space
Web server: a minimum of 5GB is required. However, this depends largely on the availability / necessity of a file server. If the customer will be offering e.g. videos, much more disk space may be necessary. Infor cannot make recommendations as this will depend on what the customer will be making available to its target audience.
Database server: initially 5GB is sufficient for the Iguana database / namespace.
|
|
However, most of the database will be used by transaction data that is stored for later statistical analysis. Depending on the number of sessions and actions on the site, the amount of required disk space may increase significantly over time. This will need to be assessed for each individual implementation. |
1.3 Hardware recommendations
We recommend using modern and up-to-date hardware for both the web server and the database server. We also recommend conferring with our PS department about the specific recommendations/requirements for these servers depending on the client situation, taking into account expected traffic, number of visitors and similar factors.
1.4 Additional requirements Web server
The following requirements apply with regard to pre-installed software and access rights and privileges (for Infor).
1. PHP 5.x with GD2, CURL and SOAP modules installed.
allow_url_fopen must be enabled.
See also 1.4.2.
2. If possible, the possibility to adapt this setting or access to php.ini.
3. FTP access, including management tool for user management. Creating / removing folders, removing files etc. must be possible through FTP.
4. PHP & FTP (and other) users must have the same rights i.e. that PHP files / directories made with FTP can manage (remove etc.) and vice versa, etc.
5. Script-enabled external access, i.e. that (PHP) scripts on the web server can retrieve data from an external server (e.g. by calling a URL/web service on an external server) without restrictions. For this external access, proxy servers are not supported.
6. Access to IIS/Apache.
If Apache, the possibility to manage/upload .htaccess file.
If IIS7, the IIS Administration Pack (http://www.iis.net/download/administrationpack) needs be installed so that the Configuration Editor is available. This will also ensure that each virtual directory defined in IIS has a web.config file. This pack has been integrated into IIS7.5 so it does not apply to IIS7.5.
7. For Apache we advise version 2.2.x.
8. The web server (Apache/IIS) should be configured to work with the installed PHP version. See also 1.4.2.
9. Possibility to log on to the web server for the installation of the Caché gateway software and configuration of IIS/Apache, for example through Remote Desktop.
10. Optional: Telnet access. If Telnet access is available (on an Apache web server), possibility to use htpasswd.
1.4.1 Ports on the web server
The above requirements imply that a number of ports must be opened. Typically these will be:
· Web server : port 80
· FTP on the web server : port 21
· SFTP on the web server : port 22
· Telnet on the web server : port 23.
|
|
Please note that either FTP or SFTP is required, - not both. |
|
|
Telnet access is, as mentioned before, optional, and only relevant for Unix/Linux. |
1.4.2 Comments on installing PHP
For more information on how to install PHP on the various web server/OS combinations, please see http://www.php.net/manual/en/install.php, and the manuals linked from there. Note that in some cases the recommended installation requires manual installation using a ZIP package, and not the installer package.
PHP comes in 2 flavours: a thread safe version and a non-thread safe version. It is recommended to check the appropriate manual for the correct version to install, however here is a brief, though incomplete, checklist (taken from http://www.php.net/manual/en/install.windows.manual.php):
· If PHP is used with IIS then choose PHP 5.3 VC9 Non Thread Safe or PHP 5.2 VC6 Non Thread Safe;
· If PHP is used with IIS7 or greater and PHP 5.3+, then the VC9 binaries of PHP should be used.
· If PHP is used with Apache 1 or Apache 2 then choose PHP 5.3 VC6 or PHP 5.2 VC6.
Please check the specific installation manual for more information before downloading a PHP package.
Also note that there is no official 64bit version of PHP5. This is not a problem for running PHP on a 64bit OS except with IIS6. IIS6 can be set up to work correctly with the 32bit PHP5, but it will not be able to pass Caché requests (.cls, .csp) correctly anymore, as the Caché gateway will still be 64bit and IIS6 cannot handle 32bit and 64bit applications at the same time. So in that case we recommend either upgrading to IIS7/IIS7.5, or using an unofficial 64bit build of PHP, which can be found for instance here: http://www.anindya.com/php-5-3-5-x64-64-bit-for-windows/ and continuing from there with the regular PHP5 / IIS6 setup.
For installing PHP on Linux/Unix please check the installation manual/procedure supplied by the Linux/Unix vendor. Typically the vendor supplies a manual/procedure and installation package for PHP (and a web server such as Apache). There are also general instructions available on the aforementioned page http://www.php.net/manual/en/install.php
1.5 Additional requirements database server
The following requirements apply with regard to pre-installed software and access rights and privileges (for Infor).
1. Access to the database server through Remote Desktop. User must have sufficient rights to install software (Intersystems Caché). Access to the Caché System Management Environment, Caché Studio and Caché Terminal.
2. The database server must have access to a mail server (for sending forms, and other aspects such as log reports), which must be able to send mail outwards (outside the domain where the database server operates). This server must support the SMTP protocol.
3. If the web server is separate from the database server, the database server must allow external access (i.e. from the web server) on port 1972.
4. Optional: Telnet/FTP access (this is not relevant if RDP access is possible).
1.5.1 Ports on the database server
The above requirements imply that a number of ports must be opened. Typically these will be:
· FTP on the database server : port 21
· SFTP on the database server : port 22
· Telnet on the database server : port 23.
|
|
Please note that either FTP or SFTP is required, - not both. |
|
|
Telnet access is not relevant if RDP access is available. |
2 Client-side
2.1 Supported browsers
The following browsers are supported:
· Firefox: latest version
· Chrome: latest version
· Safari: latest version
· Internet Explorer: recommend version 9 or higher, minimum version 8
This applies to the use of both the Iguana CMS and the front-end. Or course we realize you have no control over what browsers your customers use. But you can put this recommendation in a statement on your Iguana portal.
Please note
These are the requirements at the time of initial delivery of this release. These requirements may change over the lifetime of a release. For latest information on technical requirements one should look for the STE (Supported Technical Environments document) on InforXtreme or consult Infor support.
The above list of supported browsers and browser versions does not imply that Iguana will not work with other browsers or browser versions. The supported browsers and browser versions is the reflection of which browsers and which browser versions were tested in combination with Iguana.
A Flash plug-in is mandatory if Flash animations are included in a site's content; the minimal required Flash version is version 10. However, if you include animations in a site's content and there is no Flash Player installed on the user's device, Iguana will automatically switch to a JavaScript based animation.
· Document control - Change History
|
Version |
Date |
Change description |
Author |
| ||
| 0.1 |
Spring 2010 |
Original Dutch version |
Edwin Heijmen |
| ||
| 0.2 |
November 2010 |
Translated to English |
Tamir Borensztajn |
| ||
| 0.3 |
November 2010 |
Smaller changes |
Paul Clemens |
| ||
| 1.0 |
November 2010 |
Smaller changes ; final review of version 1 |
|
| ||
| 2.0 |
August 2011 |
Version 2 updates |
Edwin Heijmen |
| ||
| 2.1 |
November 2011 |
Reformatting |
Dave Alexander |
| ||
| 2.2 |
December 2011 |
Included as chapter of user documentation |
|
| ||
| 2.3 |
January 2012 |
Added header |
|
| ||
| 2.4 |
January 2012 |
Added more information on supported on supported browsers and Flash player |
|
| ||
| 2.5 |
January 2012 |
Reviewed Added additional information on required disk space |
|
| ||
| 2.6 |
January 2012 |
Added information on ports Processed remarks from additional review by EH |
|
| ||
| 3.0 |
May 2012 |
Reformat for online help doc |
|
| ||
| 4.0 |
February 2013 |
Minor updates |
|
| ||
| 5.0 |
April 2016 |
General update |
|
|||